K2GO-422 feat(forgejo): post-install "Install repos" action + status endpoint - #593

On an installed Forgejo, the module detail now offers "Install example
repositories" when the box status (GET /forgejo/status) says the forge is
manageable and has no repos yet. Tapping it enqueues the seed to the tasks index
Get More style: bank the seed, start the foreground ForgejoSeedService, and open
SetupProgressActivity, which tracks the running seed to completion via a new
EXTRA_FORGEJO_SEED launch flag.

- ForgejoStatusClient: reads the box status; canInstallRepos / hasRepos / blocked.
- SetupProgressActivity: EXTRA_FORGEJO_SEED marks a post-install seed run, so the
  completion gate waits on it (seedPendingRun = ... && (moduleShown ||
  postInstallSeed)) and the seed row shows. The stranded case (a banked seed
  leaking into an unrelated Get More flow) has neither signal, so it still does
  not block: no hang reintroduced.
- ModuleDetailFragment: the installed branch queries the status off the main
  thread and shows "Install repos", nothing (repos present), or a blocked note
  (an admin exists that K2Go cannot authenticate).

Update/refresh of existing repos (non-destructive) remains a later deliverable
(K2GO-422 section A). New strings are parked for translation before merge.

…action

Device test: the "Install repos" button returned "done" in ~6 ms without
seeding. The box seed status is a single shared marker; the prior admin/org seed
left it "done", and ForgejoSeedClient.drive short-circuits on a leftover "done"
before it POSTs (finding D, deferred from the analysis, now hit).

Add drive(includeRepos, force, listener): force ignores the leftover "done" and
POSTs a fresh seed (the box POST rewrites the status to "running" synchronously,
so the poll follows the fresh run); non-forced keeps the re-attach optimization
for the install flow. ForgejoSeedService.start(ctx, force) threads it; the
post-install button forces. Device-validated on arm64: the seed ran ~58 s and
adopted the 3 example repos.

Two-pass review follow-ups on the status path:
- ForgejoStatusClient: raise the read timeout to 30s. The box makes a couple of
  short forge calls before answering, and a 10s client timeout could expire on a
  warming forge, silently hiding the "Install repos" button.
- forgejo.status.ts: run the independent probes (public users lookup + authed
  /user) with Promise.allSettled instead of sequentially, and lower the per-call
  timeout to 5s, so the worst-case latency is roughly halved.

…t/K2GO-422-forgejo-repos-post-install

… locales

Migrate k2go_forgejo_install_repos and k2go_forgejo_repos_blocked from
strings_untranslated.xml into strings.xml (English) and all 33 locale files.
Machine translations, marked for human review. Tracker is empty again.

Third-pass review: seedPendingRun released the completion gate on
mq.didFail("forgejo") in the post-install flow too, where the module queue is a
stale/unrelated verdict. Scope it to moduleShown so a post-install seed run
waits on its own state. Behavior-preserving for the module-install and
post-install flows; closes the fragile coupling.